-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add (dummy) dispatch.dropExports to liveslots, test that it can be called #2656
Conversation
a470720
to
ff94e1c
Compare
b19e9b1
to
074c8a9
Compare
ff94e1c
to
613c165
Compare
This new version (613c165) adds |
Oops, I have one more commit to add to this, I forgot to wire Also, it's failing because of some XS thing.. which I thought I made optional, weird. |
074c8a9
to
e4f869e
Compare
67dade8
to
da1c505
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside from the repeated boilerplate in all the vat workers, which we already know is a more general issue, this looks fine to me.
6713c50
to
f9b5133
Compare
068fb62
to
2b7b09b
Compare
There's a small overlap between this and #2680, so I'm going to hold off landing it until that one lands. |
2b7b09b
to
b1080f0
Compare
…gers The new `dropExports()` doesn't do anything yet, but at least test that it can be called directly in liveslots and comms. It should be reachable through all vat worker types, but I won't be able to test that until we have a kernel mechanism to provoke it. closes #2653
b1080f0
to
9fabfdf
Compare
The new
dropExports()
doesn't do anything yet, but at least test that itcan be called directly in liveslots. It should be reachable through all vat
worker types, but I won't be able to test that until we have a kernel
mechanism to provoke it.
closes #2653
refs #2615